-- Network Working Group S. Kille, WG Chair
-- Request for Comments: 1566 ISODE Consortium
-- Category: Standards Track N. Freed, Editor
-- Innosoft
-- January 1994
--
--
-- Mail Monitoring MIB
--MTA-MIB DEFINITIONS::=BEGINIMPORTSOBJECT-TYPE,Counter32,Gauge32FROM SNMPv2-SMI
DisplayString,TimeIntervalFROM SNMPv2-TC
mib-2
FROM RFC1213-MIB
applIndex
FROM APPLICATION-MIB;mta MODULE-IDENTITYLAST-UPDATED"9311280000Z"
ORGANIZATION"IETF Mail and Directory Management Working Group"CONTACT-INFO" Ned Freed
Postal: Innosoft International, Inc.
250 West First Street, Suite 240
Claremont, CA 91711
US
Tel: +1 909 624 7907
Fax: +1 909 621 5319
E-Mail: ned@innosoft.com"DESCRIPTION"The MIB module describing Message Transfer Agents (MTAs)"::={ mib-2 28}mtaTable OBJECT-TYPESYNTAXSEQUENCEOF MtaEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The table holding information specific to an MTA."
::={mta 1}mtaEntry OBJECT-TYPESYNTAX MtaEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The entry associated with each MTA."INDEX{applIndex}::={mtaTable 1}
MtaEntry ::=SEQUENCE{
mtaReceivedMessages
Counter32,
mtaStoredMessages
Gauge32,
mtaTransmittedMessages
Counter32,
mtaReceivedVolume
Counter32,
mtaStoredVolume
Gauge32,
mtaTransmittedVolume
Counter32,
mtaReceivedRecipients
Counter32,
mtaStoredRecipients
Gauge32,
mtaTransmittedRecipients
Counter32}mtaReceivedMessages OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of messages received since MTA initialization."::={mtaEntry 1}
mtaStoredMessages OBJECT-TYPESYNTAXGauge32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of messages currently stored in the MTA."::={mtaEntry 2}mtaTransmittedMessages OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of messages transmitted since MTA initialization."::={mtaEntry 3}mtaReceivedVolume OBJECT-TYPE
SYNTAXCounter32UNITS"K-octets"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total volume of messages received since MTA
initialization, measured in kilo-octets. This volume should
include all transferred data that is logically above the mail
transport protocol level. For example, an SMTP-based MTA
should use the number of kilo-octets in the message header
and body, while an X.400-based MTA should use the number of
kilo-octets of P2 data."::={mtaEntry 4}mtaStoredVolume OBJECT-TYPESYNTAXGauge32UNITS"K-octets"
MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total volume of messages currently stored in the MTA,
measured in kilo-octets. This volume should include all
stored data that is logically above the mail transport
protocol level. For example, an SMTP-based MTA should
use the number of kilo-octets in the message header and
body, while an X.400-based MTA would use the number of
kilo-octets of P2 data."::={mtaEntry 5}mtaTransmittedVolume OBJECT-TYPESYNTAXCounter32UNITS"K-octets"MAX-ACCESSread-onlySTATUScurrent
DESCRIPTION"The total volume of messages transmitted since MTA
initialization, measured in kilo-octets. This volume should
include all transferred data that is logically above the mail
transport protocol level. For example, an SMTP-based MTA
should use the number of kilo-octets in the message header
and body, while an X.400-based MTA should use the number of
kilo-octets of P2 data."::={mtaEntry 6}mtaReceivedRecipients OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of recipients specified in all messages
received since MTA initialization. Recipients this MTA
had no responsibility for should not be counted even if
information about such recipients is available."::={mtaEntry 7}mtaStoredRecipients OBJECT-TYPESYNTAXGauge32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of recipients specified in all messages
currently stored in the MTA. Recipients this MTA had no
responsibility for should not be counted."::={mtaEntry 8}mtaTransmittedRecipients OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrent
DESCRIPTION"The total number of recipients specified in all messages
transmitted since MTA initialization. Recipients this MTA
had no responsibility for should not be counted."::={mtaEntry 9}-- MTAs typically group inbound reception, queue storage, and-- outbound transmission in some way. In the most extreme case-- information will be maintained for each different entity that-- receives messages and for each entity the MTA stores messages for-- and delivers messages to. Other MTAs may elect to treat all-- reception equally, all queue storage equally, all deliveries-- equally, or some combination of this.-- In any case, a grouping abstraction is an extremely useful for
-- breaking down the activities of an MTA. For purposes of labelling-- this will be called a "group" in this MIB.-- Each group contains all the variables needed to monitor all aspects-- of an MTA's operation. However, the fact that all groups contain-- all possible variables does not imply that all groups must use all-- possible variables. For example, a single group might be used to-- monitor only one kind of event (inbound processing, outbound-- processing, or storage). In this sort of configuration all unused-- counters would be inaccessible; e.g., returning either a-- noSuchName error (for an SNMPv1 get), or a noSuchInstance-- exception (for an SNMPv2 get).-- Groups are not necessarily mutually exclusive. A given event may-- be recorded by more than one group, a message may be seen as
-- stored by more than one group, and so on. Groups should be all-- inclusive, however: if groups are implemented all aspects of an-- MTA's operation should be registered in at least one group. This-- freedom lets implementors use different sets of groups to-- provide differents "views" of an MTA.-- The possibility of overlap between groups means that summing-- variables across groups may not produce values equal to those in-- the mtaTable. mtaTable should always provide accurate information-- about the MTA as a whole.-- The term "channel" is often used in MTA implementations; channels-- are usually, but not always, equivalent to a group. However,-- this MIB does not use the term "channel" because there is no-- requirement that an MTA supporting this MIB has to map its
-- "channel" abstraction one-to-one onto the MIB's group abstration.mtaGroupTable OBJECT-TYPESYNTAXSEQUENCEOF MtaGroupEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The table holding information specific to each MTA group."::={mta 2}mtaGroupEntry OBJECT-TYPESYNTAX MtaGroupEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The entry associated with each MTA group."INDEX{applIndex, mtaGroupIndex}
::={mtaGroupTable 1}
MtaGroupEntry ::=SEQUENCE{
mtaGroupIndex
INTEGER,
mtaGroupReceivedMessages
Counter32,
mtaGroupRejectedMessages
Counter32,
mtaGroupStoredMessages
Gauge32,
mtaGroupTransmittedMessages
Counter32,
mtaGroupReceivedVolume
Counter32,
mtaGroupStoredVolume
Gauge32,
mtaGroupTransmittedVolume
Counter32,
mtaGroupReceivedRecipients
Counter32,
mtaGroupStoredRecipients
Gauge32,
mtaGroupTransmittedRecipients
Counter32,
mtaGroupOldestMessageStored
TimeInterval,
mtaGroupInboundAssociations
Gauge32,
mtaGroupOutboundAssociations
Gauge32,
mtaGroupAccumulatedInboundAssociations
Counter32,
mtaGroupAccumulatedOutboundAssociations
Counter32,
mtaGroupLastInboundActivity
TimeInterval,
mtaGroupLastOutboundActivity
TimeInterval,
mtaGroupRejectedInboundAssociations
Counter32,
mtaGroupFailedOutboundAssociations
Counter32,
mtaGroupInboundRejectionReason
DisplayString,
mtaGroupOutboundConnectFailureReason
DisplayString,
mtaGroupScheduledRetry
TimeInterval,
mtaGroupMailProtocol
OBJECTIDENTIFIER,
mtaGroupName
DisplayString}mtaGroupIndex OBJECT-TYPESYNTAXINTEGER(1..2147483647)MAX-ACCESSnot-accessibleSTATUScurrent
DESCRIPTION"The index associated with a group for a given MTA."::={mtaGroupEntry 1}mtaGroupReceivedMessages OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of messages received to this group since MTA
initialization."::={mtaGroupEntry 2}mtaGroupRejectedMessages OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrent
DESCRIPTION"The number of messages rejected by this group since MTA
initialization."::={mtaGroupEntry 3}mtaGroupStoredMessages OBJECT-TYPESYNTAXGauge32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of messages currently stored in this
group's queue."::={mtaGroupEntry 4}mtaGroupTransmittedMessages OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-only
STATUScurrentDESCRIPTION"The number of messages transmitted by this group since MTA
initialization."::={mtaGroupEntry 5}mtaGroupReceivedVolume OBJECT-TYPESYNTAXCounter32UNITS"K-octets"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total volume of messages received to this group since
MTA initialization, measured in kilo-octets. This volume
should include all transferred data that is logically above
the mail transport protocol level. For example, an
SMTP-based MTA should use the number of kilo-octets in the
message header and body, while an X.400-based MTA should use
the number of kilo-octets of P2 data."::={mtaGroupEntry 6}mtaGroupStoredVolume OBJECT-TYPESYNTAXGauge32UNITS"K-octets"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total volume of messages currently stored in this
group's queue, measured in kilo-octets. This volume should
include all stored data that is logically above the mail
transport protocol level. For example, an SMTP-based
MTA should use the number of kilo-octets in the message
header and body, while an X.400-based MTA would use the
number of kilo-octets of P2 data."
::={mtaGroupEntry 7}mtaGroupTransmittedVolume OBJECT-TYPESYNTAXCounter32UNITS"K-octets"MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total volume of messages transmitted by this group
since MTA initialization, measured in kilo-octets. This
volume should include all transferred data that is logically
above the mail transport protocol level. For example, an
SMTP-based MTA should use the number of kilo-octets in the
message header and body, while an X.400-based MTA should use
the number of kilo-octets of P2 data."::={mtaGroupEntry 8}
mtaGroupReceivedRecipients OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of recipients specified in all messages
received to this group since MTA initialization.
Recipients this MTA had no responsibility for should not
be counted."::={mtaGroupEntry 9}mtaGroupStoredRecipients OBJECT-TYPESYNTAXGauge32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of recipients specified in all messages
currently stored in this group's queue. Recipients this
MTA had no responsibility for should not be counted."::={mtaGroupEntry 10}mtaGroupTransmittedRecipients OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of recipients specified in all messages
transmitted by this group since MTA initialization.
Recipients this MTA had no responsibility for should not
be counted."::={mtaGroupEntry 11}mtaGroupOldestMessageStored OBJECT-TYPESYNTAXTimeInterval
MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Time since the oldest message in this group's queue was
placed in the queue."::={mtaGroupEntry 12}mtaGroupInboundAssociations OBJECT-TYPESYNTAXGauge32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of current associations to the group, where the
group is the responder."::={mtaGroupEntry 13}mtaGroupOutboundAssociations OBJECT-TYPE
SYNTAXGauge32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of current associations to the group, where the
group is the initiator."::={mtaGroupEntry 14}mtaGroupAccumulatedInboundAssociations OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of associations to the group since MTA
initialization, where the group is the responder."::={mtaGroupEntry 15}
mtaGroupAccumulatedOutboundAssociations OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of associations from the group since MTA
initialization, where the group was the initiator."::={mtaGroupEntry 16}mtaGroupLastInboundActivity OBJECT-TYPESYNTAXTimeIntervalMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Time since the last time that this group had an active
inbound association for purposes of message reception."
::={mtaGroupEntry 17}mtaGroupLastOutboundActivity OBJECT-TYPESYNTAXTimeIntervalMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Time since the last time that this group had an
outbound association for purposes of message delivery."::={mtaGroupEntry 18}mtaGroupRejectedInboundAssociations OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION
"The total number of inbound associations the group has
rejected, since MTA initialization."::={mtaGroupEntry 19}mtaGroupFailedOutboundAssociations OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number associations where the group was the
initiator and association establishment has failed,
since MTA initialization."::={mtaGroupEntry 20}mtaGroupInboundRejectionReason OBJECT-TYPESYNTAXDisplayStringMAX-ACCESSread-only
STATUScurrentDESCRIPTION"The failure reason, if any, for the last association this
group refused to respond to. An empty string indicates that
the last attempt was successful. If no association attempt
has been made since the MTA was initializaed the value
should be 'never'."::={mtaGroupEntry 21}mtaGroupOutboundConnectFailureReason OBJECT-TYPESYNTAXDisplayStringMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The failure reason, if any, for the last association attempt
this group initiated. An empty string indicates that the last
attempt was successful. If no association attempt has been
made since the MTA was initialized the value should be
'never'."::={mtaGroupEntry 22}mtaGroupScheduledRetry OBJECT-TYPESYNTAXTimeIntervalMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The time when this group is scheduled to next attempt to
make an association."::={mtaGroupEntry 23}mtaGroupMailProtocol OBJECT-TYPESYNTAXOBJECTIDENTIFIERMAX-ACCESSread-only
STATUScurrentDESCRIPTION"An identification of the protocol being used by this group.
For an group employing OSI protocols, this will be the
Application Context. For Internet applications, the IANA
maintains a registry of the OIDs which correspond to well-known
message transfer protocols. If the application protocol is
not listed in the registry, an OID value of the form
{applTCPProtoID port} or {applUDProtoID port} are used for
TCP-based and UDP-based protocols, respectively. In either
case 'port' corresponds to the primary port number being
used by the group. applTCPProtoID and applUDPProtoID are
defined in [5]."::={mtaGroupEntry 24}mtaGroupName OBJECT-TYPESYNTAXDisplayString
MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"A descriptive name for the group. If this group connects to
a single remote MTA this should be the name of that MTA. If
this in turn is an Internet MTA this should be the domain name.
For an OSI MTA it should be the string encoded distinguished
name of the managed object using the format defined in RFC-1485.
For X.400(1984) MTAs which do not have a Distinguished Name,
the RFC-1327 syntax 'mta in globalid' should be used."::={mtaGroupEntry 25}mtaGroupAssociationTable OBJECT-TYPESYNTAXSEQUENCEOF MtaGroupAssociationEntry
MAX-ACCESSnot-accessible
STATUScurrentDESCRIPTION"The table holding information regarding the associations
for each MTA group."::={mta 3}mtaGroupAssociationEntry OBJECT-TYPESYNTAX MtaGroupAssociationEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The entry holding information regarding the associations
for each MTA group."INDEX{applIndex, mtaGroupIndex, mtaGroupAssociationIndex}::={mtaGroupAssociationTable 1}
MtaGroupAssociationEntry ::=SEQUENCE{
mtaGroupAssociationIndex
INTEGER}mtaGroupAssociationIndex OBJECT-TYPESYNTAXINTEGER(1..2147483647)MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Reference into association table to allow correlation of
this group's active associations with the association table."::={mtaGroupAssociationEntry 1}-- Conformance informationmtaConformance OBJECTIDENTIFIER::={mta 4}
mtaGroups OBJECTIDENTIFIER::={mtaConformance 1}mtaCompliances OBJECTIDENTIFIER::={mtaConformance 2}-- Compliance statementsmtaCompliance MODULE-COMPLIANCESTATUScurrentDESCRIPTION"The compliance statement for SNMPv2 entities which
implement the Mail Monitoring MIB for basic
monitoring of MTAs."MODULE-- this moduleMANDATORY-GROUPS{mtaGroup}
::={mtaCompliances 1}mtaAssocCompliance MODULE-COMPLIANCESTATUScurrentDESCRIPTION"The compliance statement for SNMPv2 entities which
implement the Mail Monitoring MIB for monitoring of
MTAs and their associations."MODULE-- this moduleMANDATORY-GROUPS{mtaGroup, mtaAssocGroup}::={mtaCompliances 2}-- Units of conformancemtaGroup OBJECT-GROUPOBJECTS{
mtaReceivedMessages, mtaStoredMessages,
mtaTransmittedMessages, mtaReceivedVolume, mtaStoredVolume,
mtaTransmittedVolume, mtaReceivedRecipients,
mtaStoredRecipients, mtaTransmittedRecipients,
mtaGroupReceivedMessages, mtaGroupRejectedMessages,
mtaGroupStoredMessages, mtaGroupTransmittedMessages,
mtaGroupReceivedVolume, mtaGroupStoredVolume,
mtaGroupTransmittedVolume, mtaGroupReceivedRecipients,
mtaGroupStoredRecipients, mtaGroupTransmittedRecipients,
mtaGroupOldestMessageStored, mtaGroupInboundAssociations,
mtaGroupOutboundAssociations,
mtaGroupAccumulatedInboundAssociations,
mtaGroupAccumulatedOutboundAssociations,
mtaGroupLastInboundActivity, mtaGroupLastOutboundActivity,
mtaGroupRejectedInboundAssociations,
mtaGroupFailedOutboundAssociations,
mtaGroupInboundRejectionReason,
mtaGroupOutboundConnectFailureReason,
mtaGroupScheduledRetry, mtaGroupMailProtocol, mtaGroupName}STATUScurrentDESCRIPTION"A collection of objects providing basic monitoring of MTAs."::={mtaGroups 1}mtaAssocGroup OBJECT-GROUP
OBJECTS{
mtaGroupAssociationIndex}STATUScurrentDESCRIPTION"A collection of objects providing monitoring of MTA
associations."::={mtaGroups 2}END